Repository navigation
ci: stop publishing the alien CLI distribution from this repo - #883
Merged
Merged
Conversation
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
The stable release built the `alien` executable from a separately pinned external composition. That pin went stale, and it compiled a combination of sources that no other CI job tested. This repository now publishes only what it builds from its own source: crates, npm libraries, native addons, the AI gateway, client SDKs, Python wheels, container images, the OSS binaries in the release bucket, and a GitHub release carrying the changelog. The `alien` executable, `@alienplatform/cli`, the Homebrew formula and the `channels/stable` pointer are published by the official CLI distribution, from this repository's release tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ease The GitHub release keeps archives that include the alien CLI, and immutable releases cannot gain assets after publication, so the release is created by the distribution that builds the CLI, from this tag. The changelog is rendered there from cliff.toml. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
alongubkin
force-pushed
the
alon/alien-1228-official-cli-from-platform
branch
from
October 5, 2026 11:48
a4da5c8 to
a366c5e
Compare
Member
Author
|
@greptileai review |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The stable release built the
alienexecutable from a separately pinned external composition. That pin went stale, and the release compiled a combination of sources that no other CI job tested.What
This repository now publishes only what it builds from its own source:
alien-base,alien-worker-typescript,alien-builder,alien-operator,alien-manager,alien-sandbox-agent)releases.alien.dev:alien-deploy,alien-operator,alien-manager,alien-worker-runtimeThese move to the official CLI distribution, which publishes them from this repository's release tag after the release: the
alienexecutable,@alienplatform/cli, the GitHub release, the Homebrew formula andchannels/stable.The GitHub release keeps the same archives as every earlier release (
alienplus this release's binaries per target, and checksums). Immutable releases can't gain assets after they're published, so the release has to be created by whatever buildsalien. This workflow now creates only the tag; the distribution then creates the release on it, with the changelog rendered fromcliff.tomlovervPREV..vX.Removed:
.github/official-cli-platform-revision, plus the extra checkout and build in the four binary jobs. Cache keys go to-b2because the cached set changed.qualify-github-releaseandgenerate-changelog.create-github-releasebecomescreate-release-tag: it keeps the immutable-release and tag-ruleset checks, then creates the tag at the qualified commit, or verifies it if it already exists.publish-homebrew-tap,publish-stable-channel,qualify-npm-cli-wrapper,publish-npm-cli-wrapper,scripts/build-npm-packages.sh,packages/alien-cli-npm.release-stable.yml, the resume check now waits onqualify-imagesand stops requiring the removed artifacts (changelog,qualified-github-release,qualified-npm-cli).Nothing changes for clients:
alien upgrade, the install scripts andalien-deploy upstill resolvechannels/stableand download versioned objects fromreleases.alien.dev.Validation
node --test scripts/sdk-release-metadata.test.mjs scripts/release-routing.test.mjs: 9/9 pass. The routing test for the removed composition is deleted with it.actionlintreports no errors beyond the custom Depot runner labels, and no jobneedsa removed job.pnpm install --frozen-lockfile --lockfile-onlypasses with the removed package's importer dropped.The next stable release exercises the full path: OSS artifacts publish from here, then the CLI distribution follows from the tag.
🤖 Generated with Claude Code